EES-5896 Azure DevOps pipeline for Search infrastructure deployment #5628
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds an Azure DevOps pipeline to create and update Azure components defined as Bicep related to implementing site-wide search.
We would like to define the infrastructure for implementing site-wide search as Bicep, but up until now the Public API infrastructure pipeline is the only other pipeline setup to deploy configuration defined as Bicep.
At the moment we have a requirement to "Keep the Public API stable" so the intention here has been to make the least amount of changes to Public API infrastructure config in order to create a pipeline for deploying search components independently of the Public API.
At a later date a larger renaming/refactoring exercise will probably be needed to organise common resources and variables.